An ITMS-91061: Missing privacy manifest rejection email looks as follows: ITMS-91061: Missing privacy manifest- Your app includes "<path/to/SDK>", which includes , an SDK that was identified in the documentation as a privacy-impacting third-party SDK. Starting February 12, 2025, if a new app includes a privacy-impacting SDK, or an app update adds a new privacy-impacting SDK, the SDK must include a privacy manifest file. Please contact the provider of the SDK that includes this file to get an updated SDK version with a privacy manifest. For more details about this policy, including a list of SDKs that are required to include signatures and manifests, visit: https://developer.apple.com/support/third-party-SDK-requirements. Glossary ITMS-91061: Missing privacy manifest: An email that includes the name and path of privacy-impacting SDK(s) with no privacy manifest files in your app bundle. For more information, see https://developer.apple.com/support/third-party-SDK-requirements. : The specified privacy-impacting SDK that doesn't include a privacy manifest file. If you are the developer of the rejected app, gather the name of the SDK from the email you received from Apple, then contact the SDK's provider for an updated version that includes a valid privacy manifest. After receiving an updated version of the SDK, verify the SDK includes a valid privacy manifest file at the expected location. For more information, see Adding a privacy manifest to your app or third-party SDK. If your app includes a privacy manifest file, make sure the file only describes the privacy practices of your app. Do not add the privacy practices of the SDK to your app's privacy manifest. If the email lists multiple SDKs, repeat the above process for all of them. If you are the developer of an SDK listed in the email, publish an updated version of your SDK that includes a privacy manifest file with valid keys and values. Every privacy-impacting SDK must contain a privacy manifest file that only describes its privacy practices. To learn how to add a valid privacy manifest to your SDK, see the Additional resources section below. Additional resources Privacy manifest files Describing data use in privacy manifests Describing use of required reason API Adding a privacy manifest to your app or third-party SDK TN3182: Adding privacy tracking keys to your privacy manifest TN3183: Adding required reason API entries to your privacy manifest TN3184: Adding data collection details to your privacy manifest TN3181: Debugging an invalid privacy manifest

In this post, we'll share tips to help you submit apps that deliver original ideas to your users. When working on your app, focus on creating interesting, unique experiences that aren't already available. Apps that actively try to copy other apps won't pass review, and accounts that repeatedly submit copycat apps or attempt to impersonate a service will be closed. The rules that prevent copycat and impersonator apps from being distributed on the App Store are described in App Review Guideline 4.1: 4.1 Copycats (a) Come up with your own ideas. We know you have them, so make yours come to life. Don’t simply copy the latest popular app on the App Store, or make some minor changes to another app’s name or UI and pass it off as your own. In addition to risking an intellectual property infringement claim, it makes the App Store harder to navigate and just isn’t fair to your fellow developers. (b) Submitting apps which impersonate other apps or services is considered a violation of the Developer Code of Conduct and may result in removal from the Apple Developer Program.(c) You cannot use another developer’s icon, brand, or product name in your app’s icon or name, without approval from the developer. These requirements help make the App Store both a safe place for people to discover apps and a platform for all developers to be successful. Best Practices Here are three best practices that will help you submit apps that follow App Review Guideline 4.1: 1. Submit apps with unique content and features. People want apps that provide unique experiences. Find areas that aren't currently being served and build compelling apps for those audiences. Do: Create apps that provide a new experience or a unique spin on an existing concept. Design original, delightful interfaces that elegantly meet your user's needs. Don't: Don’t imitate the features and functionality of other apps. Don’t copy the look and feel of other apps, such as using an identical user interface design. 2. Make sure App Store metadata only contains relevant information and content you either own or have permission to use. The metadata provided in App Store Connect is used to populate your app's product page on the App Store. People rely on this metadata to learn about your app and what it has to offer. Leveraging the popularity of another brand or app, either by including irrelevant references or protected content, is misleading and won't help your app succeed. Do: Use engaging, descriptive language to describe your unique app. Create original content that best represents your app, such as screenshots showing the actual app in use. Don't: Don't use protected material you do not have the necessary permission to use, such as app icons that are similar to icons of a popular app. Don’t include irrelevant references, such as popular app names or trademarked terms, in any metadata fields. 3. Provide information that is authentic and verifiable. People want to know the developers behind their favorite apps are who they say they are. It's important to continually review and provide up-to-date information, including the developer or company name listed on your Apple Developer Program account, the Support URL listed on your app's product page, and other helpful information. This will enable your users to contact you when they need help and it will also hinder people who may try to impersonate you, your app, or your service. Do: Make sure all information, resources, and documentation related to your account and apps are current and accurate. Don't: Don’t provide inaccurate information or resources, such as directing people to outdated support pages. Don’t provide fraudulent documentation. Accounts that submit fraudulent documentation will be removed from the Apple Developer Program. Support Incorporating these best practices into your app's development will help you submit apps that follow App Review Guideline 4.1. If you need additional assistance, consider taking advantage of one of the following support options available from App Review: If your submission has been rejected, reply to the message from App Review in App Store Connect and request clarification. Request an App Review Appointment to discuss the results of our review. Appointments are subject to availability, and take place during local business hours in your region on Tuesdays and Thursdays. If you believe your app follows the App Review Guidelines, consider submitting an appeal to the App Review Board. Resources Learn about foundational design principles from Apple designers and the developer community. Learn how to create engaging App Store product pages. Note that apps that violate intellectual property rights are subject to removal through the App Store Content Dispute process. If you believe an app on the App Store violates your intellectual property rights, you can submit a claim.

We are looking for guidance on a new app submission that has not moved from "Waiting for Review". Our first submission was rejected under Guideline 5.1.1(ii). We addressed the issue the same day by updating the purpose strings to clearly describe how the requested data is used, and resubmitted immediately. The status has not changed since. Why this is time-critical: the backend service our current users depend on is being shut down by our provider on August 28, 2026. The submitted app migrates to a new provider and is the continuation of that service. Without it, our existing users will be left without a working app. What we have already tried: Submitted an expedited review request on August 23, 2026 - no response Contacted Apple through the Contact Us module several times since then - no response beyond the automated acknowledgment each time We are not asking to skip the queue for convenience. We simply need to know whether the submission is progressing normally or whether something additional is required from us. We are ready to respond to any questions from App Review immediately, at any hour. Thank you.

Hello Apple Team, We are seeking assistance regarding our app 健康行動go (App ID: 1437488996, Case ID: 20000146721382). Timeline: August 14: We received feedback regarding Guideline 4.3(a). August 21: We resolved the issues by providing detailed business differentiation, UI comparison documentation, and submitting an updated build. Status: The submission has remained in "Waiting for Review" since August 21. Today, August 27, 2026, is our scheduled public release date with external commitments. Could an Apple representative please check if our submission is held in a specialized queue and assist in escalating it to the App Review team for review? Thank you very much for your time and support.

Hello, Our app has been in "Waiting for Review" since August 23, 2026, with no status change and no messages in App Store Connect. App Name: Voxen AI Apple ID: 6790147633 Version: 1.0.0 (165) Submission ID: c827b3a4-5237-4b52-8225-d94be2b94016 Date Submitted: Aug 23, 2026 at 12:08 AM Could someone from App Review check whether this submission is stuck in the queue, or let us know if any action is needed on our side? Thank you.

i sent an emergency update to apple for my app, they rejected the update by mistake, i replied to the message and also made corrections to the app, and now the app has been waiting for review for 7 days, tried requesting an expedite no luck, tried email support no answer for 7 days, tried phone support no agent after 45 minutes wait time, idk what else to do

Apple’s App Store Enforcement Failure: Why Is “App for Instagram º” Still Approved? Apple presents the App Store as a carefully reviewed marketplace with strict rules against copycats, unauthorized use of third-party intellectual property, and misleading apps. Yet “App for Instagram º,” published by Noman Aziz, raises serious questions about whether those rules are actually being enforced. The app is currently listed on the Mac App Store as “App for Instagram º,” with the subtitle “AI tools for insta.” Apple classifies it as Social Networking, and its description says users can access Instagram, browse their feed, send and receive messages, and view profiles, posts and Reels. Most remarkably, Apple currently displays an age rating of 4+. GUIDELINE 4.1 — COPYCATS AND BRANDING Apple’s Guideline 4.1 says developers should not copy popular apps or impersonate other apps or services. Even more importantly, Guideline 4.1(c) states that a developer cannot use another developer’s icon, brand, or product name in an app’s icon or name without approval from that developer. Yet the product being distributed through Apple’s own marketplace is literally called: “App for Instagram º” The listing itself explicitly admits that it is an independent third-party application and is “not affiliated with, endorsed by, sponsored by, or associated with Instagram, Meta Platforms, Inc.” So Apple should answer one very simple question: What authorization was provided for the use of the Instagram product name and Instagram-related branding? A disclaimer buried inside an App Store description does not erase the first impression created by an application’s name, icon and overall visual presentation. Users see the name and icon before they read legal disclaimers. If Meta authorized this use, Apple should be able to confirm that the required authorization was reviewed. If no authorization exists, Apple should explain how this application complies with Guideline 4.1. GUIDELINE 5.2 — THIRD-PARTY INTELLECTUAL PROPERTY AND SERVICES The situation becomes even more serious under Apple’s intellectual-property rules. Guideline 5.2.1 says developers should not use protected third-party material, including trademarks, without permission and should not include misleading, false or copycat names, representations or metadata. Guideline 5.2.2 further states that if an application uses, accesses, monetizes access to, or displays content from a third-party service, the developer must be specifically permitted to do so under that service’s terms. This application does not merely mention Instagram. According to its own App Store description, it provides an Instagram experience on Mac, including feeds, messages, profiles, posts and Reels. It also commercially monetizes that experience through subscriptions. The Romanian App Store currently lists Weekly, Monthly and Yearly in-app purchase plans. So where is the authorization? Did Apple require the developer to demonstrate permission to access and commercially monetize this Instagram-focused experience? Did Apple verify the relevant rights before approving the application? If the answer is yes, Apple should have no difficulty confirming that appropriate authorization was reviewed. If the answer is no, then Apple needs to explain how this application passed App Review. WHY DOES AN INSTAGRAM SOCIAL NETWORKING APP HAVE A 4+ RATING? This may be the most disturbing inconsistency in the entire listing. Apple currently displays: Age Rating: 4+ At the same time, Apple categorizes the application as Social Networking, and the developer advertises access to Instagram feeds, messaging, profiles, posts and Reels. Meta itself states that users must generally be at least 13 years old to use Instagram and that it works to identify and remove accounts belonging to users under 13. Apple has also updated its age-rating framework in 2026 specifically to address social-media functionality. Apple states that apps declaring social-media capabilities — including social feeds allowing interaction with user-generated content — receive a minimum age rating of 13+. Apple says the updated questionnaire began rolling out in July 2026, with disclosure of social-media capabilities becoming mandatory for new submissions and updates starting in September 2026. So why is an application whose advertised purpose includes accessing Instagram currently presented to Mac App Store customers as 4+? To be precise, an App Store content rating and Instagram’s minimum account age are not exactly the same thing. But that does not make this situation acceptable without scrutiny. Apple’s own updated system specifically recognizes that social-media capabilities warrant a minimum 13+ classification when declared. A Social Networking application advertising Instagram feeds, messages, profiles and Reels while displaying 4+ therefore deserves immediate review. APPLE CANNOT HAVE STRICT RULES ONLY ON PAPER This is bigger than one application. It is about the credibility of Apple’s entire App Review process. Apple writes the rules. Apple reviews the application. Apple approves the name and metadata. Apple displays the age rating. Apple distributes the software. Apple processes the subscriptions. Apple therefore cannot simply distance itself from serious compliance questions when they are reported. Apple should immediately investigate: Whether the use of “Instagram” in the application name is properly authorized under Guideline 4.1. Whether the branding, icon and metadata could create a misleading impression of association with Instagram. Whether the developer has the permissions required under Guidelines 5.2.1 and 5.2.2. Whether the 4+ age rating is appropriate for an application categorized as Social Networking and advertising access to Instagram’s social-media functionality. If all necessary permissions exist and Apple believes the 4+ rating is justified, Apple should explain the basis for that conclusion. If they do not, this application should not continue benefiting from distribution and monetization through Apple’s marketplace while Apple’s published rules say something entirely different. Apple repeatedly asks developers and customers to trust the App Store review process. Trust requires consistent enforcement. Right now, this listing creates the opposite impression: strict rules exist in Apple’s documentation, while an application raising serious questions about branding, third-party rights, monetization and age classification remains publicly available. Apple should investigate this application and provide a serious, transparent answer.

Generally how much time it will take to process the enrollment.I have enrolled but it still pending, it is already 4-5 hrs, what will way to process the enrollement from apple side, should I get a call from there.I have enrolled as an organisation legal entity.

Good day, I have 2 apps, both first time submissions, stuck in review. the first one has been there since August 2nd. It doesn’t look like there is any missing metadata or other information. no error messages just ‘yellow waiting for review’. Is there anyways to check what’s holding it up? Or is just taking so long because it’s a first time submissions?

Hello, Our developer account (Team ID S9D9F72QF8) was terminated on August 24 under Section 3.2(f) for "documented indications of fraudulent conduct." We received no prior warning, no pending termination notice, and to this day no specific reason: not which app, not which action, not which signal. This account was not a side project. Our whole company, our team's livelihood, and six live apps with real users were built on it. All of it stopped overnight. We take Apple's rules extremely seriously. We have never bought or manipulated reviews, ratings, or downloads, never used misleading metadata, and never operated any other developer account. We submitted a reinstatement petition (Case 20000145868954) with a compliance improvement plan, and we offered full supporting documentation, including our trade registry records and a notarized declaration that we have no connection to any other account. We are not asking Apple to skip its process. We are asking for two things any developer would ask for: Human review of our file and petition. The specific conduct at issue, so we can respond to it with evidence. If a mistake was made on our side, we want to know it, fix it, and prove the fix. If this is a false positive, we want the chance to show it. If anyone from App Review sees this, we would be grateful for any update on our case. And if other developers have resolved a similar situation, we would appreciate hearing what helped. Thank you for reading.

Hi everyone, I submitted my new dating app and requested an expedited review because we have a launch event planned in a couple of days. Apple accepted the expedited review request, but the app is still “Waiting for Review.” If it isn't reviewed in time, we'll unfortunately have to cancel or postpone the event. Does anyone know if there is a way to contact the App Review team or a reviewer directly, or an email/support channel I can reach out to about the status of an already-approved expedited review?£ Thanks!

I'm starting to wonder if something has gone horribly wrong in the App Review department. We've had reviewers request specific information in one message, which we supplied the same day, then we wait another 4 days and they ask the same question having clearly not looked at the information we sent. We've now been completely adrift for 21 days and it's been over a week since we last heard from them. We have hundreds of people waiting on us, can't promote on social media, receiving support requests every day from customers wondering why they can't access the app. This isn't the first time we've released an app through App Store Connect, and our app is very straighforward - no restrictions or unusual requests. The app is obviously compliant, they just aren't reading any of the information we're providing, so we're totally stuck. It didn't used to be like this. A year ago we were seeing reviews turn around within the stated 24-48 hours. Has something changed in the last 6 months? Perhaps an uptick in submissions due to AI coding? Anyone else seeing these issues?

Hello, I am investigating an intermittent In-App Purchase failure that occurred during App Review for the first release of my app. Environment Review device: iPad Air 11-inch (M3) OS: iPadOS 26.6 Environment: App Review sandbox Product type: Consumable StoreKit integration: RevenueCat through react-native-purchases 10.4.3 Observed behavior StoreKit successfully returned the products, localized names, and prices. The reviewer could see the credit packs and initiate the native purchase flow. My diagnostics show this sequence: Purchase initiated PURCHASE_CANCELLED; no transaction evidence Purchase initiated again RevenueCat code 2: STORE_PROBLEM elapsed: 9.4 seconds no transaction evidence Purchase initiated again RevenueCat code 5: PRODUCT_NOT_AVAILABLE_FOR_PURCHASE no transaction evidence Purchase initiated again RevenueCat code 5: PRODUCT_NOT_AVAILABLE_FOR_PURCHASE elapsed: 0.6 seconds no transaction evidence code-block The relevant sanitized logs are: { "occurredAt": "2026-08-25T12:52:59.733Z", "platform": "ios", "appVersion": "1.0.0", "build": "14", "productId": "HIDDEN_FOR_DISPLAY", "stage": "STORE_CHECKOUT", "providerCode": "2", "providerReadableCode": "STORE_PROBLEM", "transactionEvidence": false, "elapsedMs": 9417 } code-block { "occurredAt": "2026-08-25T12:55:42.752Z", "platform": "ios", "appVersion": "1.0.0", "build": "14", "productId": "HIDDEN_FOR_DISPLAY", "stage": "STORE_CHECKOUT", "providerCode": "5", "providerReadableCode": "PRODUCT_NOT_AVAILABLE_FOR_PURCHASE", "transactionEvidence": false, "elapsedMs": 637 } code-block No App Store transaction was created, and therefore RevenueCat received no transaction or webhook for these attempts. Configuration verified I confirmed that: The affected product and the other consumable products are attached to the App Review submission. Product IDs match between the app, App Store Connect, and RevenueCat. Prices and localizations are configured. The products are available in the relevant storefronts. The Paid Apps Agreement is active. Banking and tax information are active. The In-App Purchase capability is present. The distribution build does not use a local StoreKit configuration file. The same build and affected product completed successfully afterward on a physical device using Apple Sandbox. The native purchase sheet opened, the transaction completed, and the consumable content was delivered successfully in my reproduction. The product metadata clearly remained available because its localized name and price were displayed. However, after the initial STORE_PROBLEM, subsequent purchase requests were rejected almost immediately as PRODUCT_NOT_AVAILABLE_FOR_PURCHASE. I do not have the underlying Apple NSError, such as an ASDServerErrorDomain or AMSErrorDomain value, because it was not exposed in my remote diagnostic record. Questions Can a failed sandbox transaction leave the StoreKit account/session or commerce-catalog state temporarily inconsistent, causing subsequent requests for an otherwise loaded product to return storeProductNotAvailable? Does StoreKit use separate metadata and transaction-eligibility services, allowing product information to load while the same product is rejected during purchase()? Are there known sandbox or StoreKit issues on iPadOS 26.6 that could produce this sequence? Could a stale App Review sandbox account token or storefront session explain the transition from STORE_PROBLEM to PRODUCT_NOT_AVAILABLE_FOR_PURCHASE? Is there any developer-side configuration that could explain this when the same product and binary complete successfully using another sandbox session? What additional logging should I capture from RevenueCat’s React Native SDK to preserve the complete underlying Apple error chain?

I submitted my app in August 13, 2026. But till today the app is still showing submitted for review. todays marks day 13 waiting for review. Is there anything else I should do other then expedite of which I did today (26 August 2026).

Anyone with the similar experience? Would appreciate the advice: Timeline: Initial submission: ~4 weeks ago First review: Completed after ~2 weeks after we have sent the expedited review request Fixes applied: Completed within 24 hours Resubmission: August 12, 2026 Current status: Still in review - no activity for ~2 weeks We have a planned launch date that's now at risk due to this review delay. The lack of any reviewer interaction on the resubmission is particularly concerning. Any insights or advice would be greatly appreciated

App: Linkbee (Apple ID 6798913756) Submission ID: 745fa6e5-ba33-4687-a4a3-7bb5b12005a3 Resubmitted: August 17, 2026 Our submission has been in Waiting for Review for eight days. Background: on August 14 we received a Guideline 5.6 notice. We replied in Resolution Center on August 16 explaining the cause and the fix, and resubmitted on August 17 with a corrected build. We have had no response to that reply. Is anything further required from us, or is the submission held for additional review? Happy to provide any verification needed.

Hi all, My app has been stuck in the "Waiting for Review" status since August 13 (US Time), and today is August 23. It has been 10 days without any status updates or messages from the App Review team. App ID: 6800282515 Submission Date: Aug 13, 2026 Developer Support Request Submitted: Aug 19 (No response yet) Expedited Review Requested: Aug 20 (No response yet) Current Status: Waiting for Review Since both support inquiries and expedited requests haven't received a reply after several days, I am concerned there might be an internal system hold or communication breakdown regarding this submission. Could someone from Apple please look into this or advise if any additional documentation/action is needed from my side? Thanks for your help!

Hello, My app "Kada: Learn Baybayin" (Apple ID: 6802533511) has been stuck in "Waiting for Review" status since August 19, with no transition to "In Review" as of today. This is the initial submission for version 1.0. Could someone confirm whether this is proceeding normally, or if there's anything needed from my side? Thank you for your time.

Hi - my app has been "Waiting for Review" for a week now (app id 6764576255). My past experience has been that my apps are normally reviewed within a couple of days. Is this waiting period normal at the moment?

App: AI RunCoach — App ID 6782097197, bundle ID com.airuncoach.app, Team ID 4N3X74Y2LF When adding a new build to our External Testing group, TestFlight shows: "Before you can use TestFlight to distribute beta builds of your app, you must renew your Apple Developer Program membership." Our membership is not expired: the Membership Details page shows renewal date 20 June 2027, auto-renew ON, and the €99 fee already paid. We've also checked Agreements, Tax, and Banking — nothing shows as pending or requiring action anywhere. In the meantime, our app has been stuck in "In Review" status since August 3, and TestFlight installations also seem to be blocked. A request for an expedited review produced no result, and a request for a phone consultation did not lead to any contact either. Did anyone else experience this, and could someone advise on how to contact Apple about this? Thanks in advance for any pointers.

Hi, I submitted the first version (1.0) of my iOS app for App Review on August 21, 2026, and it has now been almost 4 days. The submission is still showing “Waiting for Review” and has never changed to “In Review.” There are no messages in the Resolution Center, and I haven’t received any requests for additional information. I understand that review times can vary, especially for a first release, but I was wondering whether anyone else who submitted around August 21 is currently experiencing unusually long waiting times before the review actually starts. Is waiting 4+ days in “Waiting for Review” currently considered normal, or would it be appropriate to contact App Review Support at this point? Thanks!

Hello, 【Apple ID：6766467422，Chattoon: Voice Comic Diary】 Our app has been stuck in "In Review" status for 23 days now, and we would really appreciate any guidance or help from an Apple representative who might see this thread. Timeline: Aug 3, 2026: Submitted iOS version 1.3.0 (bug-fix-only update, no new features or permission changes) Submission ID: 993d767d-7020-454b-bf78-457bc8d8dcb7 Aug 11, 2026: Requested expedited review — request was accepted, confirmation email received (Case ID: 20000133567861) Since then: No status change. Still showing "In Review" Resolution Center: No messages, no requests for additional information Follow-up emails sent on Aug 10, Aug 13, and again this week — no response received to any of them This is a bug-fix update for our existing app (Chattoon: Voice Comic Diary), and the extended delay is now affecting our release plans. Has anyone else experienced something similar recently? Any advice on next steps, or could someone from the App Review team help check on the status of this submission? Thank you for your time.